User interface for an application displaying pages

ABSTRACT

Systems and methods for presenting information in a header region of an application are provided. In some aspects, a URL is received in an omnibox of an application window of a computer. A page corresponding to the URL is presented in a page display region of the application window. The URL is presented in the omnibox. A collapsed form of the URL and connection information associated with the page are presented in a button of the application window adjacent to the omnibox. The collapsed form of the URL includes a representation of a top-level domain and a hierarchy of the URL. The collapsed form of the URL includes different text from the URL.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority under 35 U.S. C. §119(e) and thebenefit of U.S. Provisional Application No. 61/916,714, filed Dec. 16,2013, and entitled, “USER INTERFACE FOR AN APPLICATION DISPLAYINGPAGES,” the entire disclosure of which is incorporated herein byreference.

BACKGROUND

The subject technology is generally directed to a user interface for anapplication displaying pages, for example, a web browser.

An application, for example, a web browser, may be user-customizable andinclude multiple features. However, the applications may have a simpleuser interface to allow a user to quickly access basic functions (e.g.,loading a page by typing a uniform resource locator (URL) address).Approaches for informing the user about the user-customizable featureswithout reducing the simplicity of the user interface may be desirable.

SUMMARY

In some aspects, the disclosed subject matter relates to acomputer-implemented method for updating an operating system. The methodincludes receiving, in an omnibox of an application window of acomputer, an input comprising a uniform resource locator (URL). Themethod includes presenting, in a page display region of the applicationwindow, a page corresponding to the URL. The method includes presenting,in the omnibox, the URL. The method includes presenting, in a chip ofthe application window adjacent to the omnibox, an essence of the URLand connection information associated with the page, the essence of theURL comprising a representation of a top-level domain and a hierarchy ofthe URL, the essence of the URL comprising different text from the URL.

In some aspects, the disclosed subject matter relates to anon-transitory computer-readable medium encoded with executableinstructions. The instructions include code for instantiating anapplication window, the application window comprising a header regionand a page display region, the header region comprising an omnibox. Theinstructions include code for receiving an input via the omnibox, wherethe input comprises a uniform resource locator (URL) or a search query.The instructions include code for presenting, in the page displayregion, a page in response to the received input. The instructionsinclude code for presenting, in the header region and externally to theomnibox, one or more graphical elements, the graphical elementsrepresenting permissions granted to the page or extensions having accessto the page, where the omnibox comprises text and lacks graphicalelements distinct from the text.

In some aspects, the disclosed subject matter relates to a system. Thesystem includes one or more processors and a memory. The memory includesinstructions. The instructions include code for presenting a page withina page display region of an application. The instructions include codefor receiving, via the page displayed within the page display region, arequest for one or more permissions. The instructions include code forproviding, within a bubble overlaying the page display region andadjacent to a header region of the application, a textual indication ofthe request for the one or more permissions. The instructions includecode for receiving, via the bubble, a user input for granting or denyingthe request for at least one of the one or more permissions.

It is understood that other configurations of the subject technologywill become readily apparent from the following detailed description,where various configurations of the subject technology are shown anddescribed by way of illustration. As will be realized, the subjecttechnology is capable of other and different configurations and itsseveral details are capable of modification in various other respects,all without departing from the scope of the subject technology.Accordingly, the drawings and detailed description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the subject technology are set forth in the appended claims.However, for purpose of explanation, several aspects of the disclosedsubject matter are set forth in the following figures.

FIGS. 1A-1H illustrate example user interfaces for managing action andextension icons in an application.

FIGS. 2A-2G illustrate example user interfaces for managing anapplication having an omnibox.

FIGS. 3A-3L illustrate example user interfaces for managing permissionsof an application.

FIGS. 4A-4B illustrate example windows of a web browsing application.

FIG. 5 illustrates an example computer that may provide a user interfacefor a web browsing application.

FIG. 6 illustrates an example process by which an essence of a uniformresource locator may be presented.

FIG. 7 illustrates an example process by which permissions granted to apage or an extension having access to the page may be presented.

FIG. 8 illustrates an example process by which a page may requestpermissions from a user.

FIG. 9 conceptually illustrates an example electronic system with whichsome implementations of the subject technology are implemented.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology may bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a thorough understandingof the subject technology. However, it will be clear and apparent thatthe subject technology is not limited to the specific details set forthherein and may be practiced without these specific details. In someinstances, certain structures and components are shown in block diagramform in order to avoid obscuring the concepts of the subject technology.

As set forth above, an application, such as a web browser, may includemany user-customizable features. However, to simplify the userexperience, the browser may present a very simple user interface. As aresult, teaching the user about the user-customizable features, withoutreducing the simplicity of the user interface, may be desirable.

For instance, the application may include an omnibox in which a user mayenter a uniform resource locator (URL) address or a search query. Theomnibox may include an address bar. However, some users may not knowthat the omnibox may be used to enter a search query. As the foregoingillustrates, a new approach for informing a user about the functionalityof the omnibox may be desirable.

Also, oftentimes, users access websites by selecting hyperlinks ratherthan entering a URL in an omnibox or URL input box. As a result, a usermay be fooled into accessing an invalid or insecure website (e.g.,xyzbank.badguys.com, where the user thinks he/she is accessingxyzbank.com) and providing sensitive login credentials or otherinformation to the invalid website. As the foregoing illustrates, anapproach for informing the user that he/she s accessing an invalid orinsecure website may be desirable.

In some cases, a website or application may wish to access a resource ona user's computer. For example, a website of a search engine may wish toaccess a microphone to support voice search and/or a camera to supportimage-based search. However, the user may be unfamiliar with theinterface for granting and modifying permissions for pages orapplications. As the foregoing illustrates, a new user interface forgranting and modifying permissions for pages or applications may bedesirable. As used herein, the term “page” encompasses its plain andordinary meaning Among other things, the term “page” may refer to awebsite or webpage, a page of an application executing within a webbrowser (e.g., a page of a browser application for playing the card gamesolitaire) that may not necessarily require Internet access, a page in adocument processing program, etc.

In some implementations, an application may include extension(s) oraction icon(s) that were added to the application by the user, anenterprise administrator associated with the user, or a developer of theapplication. However, the user may be unaware of the existence orfunctionality of the extension(s) or action icon(s) or the impact (e.g.,slower page loading) the extension(s) or action icon(s) are having onthe user's experience with the application. As the foregoingillustrates, a new approach for presenting the extension(s) or actionicon(s) and explaining their functionality and impact may be desirable.As used herein, the term action(s) and the term extension(s) areinterchangeable.

Actions and extensions may include additional functionality added to anapplication (e.g., functionality to play a video on an external linkedmonitor, functionality to send an article to a linked tablet computer orelectronic reader, etc.). In terms of actions and extensions,implementation(s) the subject technology may include deprecating pageactions and treating page actions like browser actions. Browser actionsmay include creating a tooltip, a badge, or a popup, and page actionsmay include taking an action on a page (e.g., transmitting the page toan external device). Implementations of the subject technology mayinclude treating some features of a browser, for instance, bookmarks,translation software, password saving, and casting to an externalmonitor, like actions. Implementations of the subject technology mayinclude removing the toolbar overflow menu that appears when users dragthe edge of the omnibox toward the overflow menu. Implementations of thesubject technology may include allowing extensions to be pinned to thetoolbar; extending toolbar reordering behavior to include droppingextension icons into the overflow menu to unpin the extension icons.Implementations of the subject technology may include making allextensions visible in the overflow menu, even the otherwise invisibleones.

FIGS. 1A-1H illustrate example user interfaces for managing action andextension icons in an application. The application may be a web browseror any other application.

FIG. 1A illustrates an example application window 100A displaying a pageof a search engine. The application window displays multiple action andextension icons 105A.1-9 displayed in the toolbar as a result of a largeamount of space in the toolbar 110A. The application window also includean omnibox 125A.

FIG. 1B illustrates an example application window 100B displaying a pageof a search engine. Similarly to FIG. 1A, the application window 100B ofFIG. 1B includes multiple action and extension icons 105B.1-9. However,due to the smaller size of the toolbar 110B, only action and extensionicons 105B.1-2 are displayed in the toolbar 110B. The remaining actionand extension icons 105B.3-9 are displayed in the overflow menu 115B,which may be presented in response to a selection of the overflow menubutton 120B. The toolbar may be made smaller and the application window100A may be changed into the application window 100B, for example, bydragging the edge of the omnibox 125A/125B in a specified direction(e.g., to the right) to make the toolbar smaller or by selecting a hidebutton (not illustrated).

FIG. 1C illustrates an example application window 100C displaying a pageof a search engine. Similarly to FIG. 1B, the application window 100C ofFIG. 1C includes action and extension icons 105C.1-15, with action andextension icons 105C.1-2 displayed in the toolbar 110C and action andextension icons 105C.3-15 displayed in multiple rows of the overflowmenu 115, which may be displayed in response to a selection of theoverflow menu button 120C. The application window 100C also includes anomnibox 125C.

FIG. 1D illustrates an example application window 100D displaying a pageof a search engine. Similarly to FIGS. 1A-1C, the application window100D of FIG. 1D includes action and extension icons 105D.1-9 all ofwhich are displayed in the overflow menu 115D and none of which aredisplayed in the toolbar 110D. The overflow menu 115D may be displayedin response to the selection of the overflow menu button 120D in thetoolbar 110D. The user may cause the application windows of FIGS. 1A-1Bto enter the state displayed in the application window 100D of FIG. 1Dby, for example, by dragging the edge of the omnibox 125A/125B/125C/125Din a specified direction (e.g., to the right) to make the toolbarsmaller or by selecting a hide button (not illustrated).

FIG. 1E illustrates an example application window 100E. As shown, anextension 105E called “WXY—Entertain Yourself” has been added to theapplication window 100E. The extension 105E may have been added by theuser or by an enterprise administrator associated with the user. As aresult of adding the extension 105E, the bubble 110E is displayed,informing the user that the extension has been added. New action andextension icons may be added to the toolbar by default. A user mayexplicitly hide an action in order to place it in the overflow menu.

FIG. 1F illustrates an example application window 100F. As shown, anextension 105F called “WXY—Entertain Yourself” has been added to theapplication window 100F. The extension 105F may have been added by theuser or by an enterprise administrator associated with the user. As aresult of adding the extension 105F or of hovering a cursor over theextension 105F, the bubble 110F is displayed, informing the user thatthe extension has access to every page the user visits and slows downthe computer. A button 115F for removing the extension from theapplication may be displayed. Certain actions or extensions, forexample, actions or extensions that slow down other operations of thecomputer or application, may be made more visible by placing them on thetoolbar rather than in the overflow menu. Furthermore, a bubble may bepointed to the action or extension explaining why the action orextension may be interesting and offering the user to remove the actionor extension. Enterprise-added actions or extensions that repeatedlycrash may be highlighted.

FIG. 1G illustrates an example application window 100G. No extensionsare shown in the toolbar 110G of the application window 100G as theextensions are hidden. As result of the extensions being hidden, theomnibox 125G is expanded to occupy more space.

FIG. 1H illustrates an example application window 100H. The applicationwindow 100H includes a translation action icon 105H. Action icons may beshown or hidden to avoid taking up extra space on the toolbar 110Hunnecessarily. The translation action icon 105H may be coupled with abubble 115H that include the text “Would you like to translate thispage?” The bubble 115H may include buttons 120H.1-2 to accept or rejectthe proposal to translate the page.

FIGS. 2A-2G illustrate example user interfaces for managing anapplication having an omnibox. The application may be a web browser orany other application.

An omnibox in an application merges the address and search fields. Inother words, the omnibox may be used both to enter a URL address (e.g.“www.example.com”) and to enter a search query (e.g., “hotels in NewYork”). Extensions may be added to an application to personalize theapplication. A bubble may be presented to allow a user to review or editpermissions given to the application or to a page in the applicationwithout accessing the settings menu. A page action may place an icon(e.g., a 16×16 pixel icon) inside the omnibox. A browser action mayplace an icon (e.g., a 19×19 pixel icon) in the toolbar to the right ofthe omnibox. The icons may be dynamic and/or animated. Unlike a browseraction, a page action may be relevant to a currently displayed page, butnot to all pages displayed by the application. A browser action may berelevant to all pages displayed by the application. Alternatively, a webbrowser may be implemented that does not distinguish between browseraction(s) and page action(s) in terms of the behavior of thebrowser/page action(s) or how the browser/page action(s) are presented.Permissions may be displayed in a page information bubble. Permissionprompts may be shown as bubbles (e.g., page action prompt bubbles) or asinformation bars. Alternatively, action(s) or extension(s) may be movedout of the omnibox, for example, into a chip that is in the toolbar andadjacent to (e.g., to the right of or to the left of) the omnibox. Thechip may be a button.

Advantageously, as a result of some implementations of the subjecttechnology, power users with multiple extensions may have control oftheir toolbar state. Also, extensions, particularly extensions havingaccess to a page, may become more visible. Malicious extensions orextensions that require more than a threshold amount of random accessmemory (e.g., more than 10% of the random access memory available to thecomputer) may be visually indicated.

FIG. 2A illustrates an application window 200A. The application window200A includes multiple action or extension icons 205A.1-9. Some actionor extension icons 205A.1-2 are displayed on the toolbar 210A, whileother action or extension icons 205A.3-9 are displayed in the overflowmenu 215A, which is presented in response to selection of the overflowmenu button 220A. The user may control which action or extension icons205A.1-9 are shown in the toolbar 210, shown in the overflow menu 220,or hidden.

FIG. 2B illustrates an application window 200B. The application window200B includes an omnibox 225B and a page information bubble 205B belowthe omnibox 225B. A lock icon 210B on the omnibox 205B indicates thatthe page displayed in an active tab of the application window 200B issecure. The page information bubble 205B includes prompts forpermissions (e.g., “Use your computer's location,” “Use your camera andmicrophone,” etc.) that the user may grant or deny to the page byselecting or de-selecting the appropriate checkboxes. In some casesdomain information or connection information (e.g., a lock icon and abackground color representing the connection information) may bepresented on the omnibox 205B in addition to or in place of the lockicon 210B. The connection information may represent, for example, anHTTP connection, an HTTPS connection, or a broken-HTTPS connection.

FIG. 2C illustrates an application window 200C with a page informationbubble 205C. The page information bubble 205C includes tabs forinformation 210C, permissions 215C, and connection 220C, where the usermay review or edit the associated information. As shown, the informationtab 210C is selected. Cookie information may be displayed via ahyperlink 230C within the information tab 210C, rather than directlywithin the information tab 210C. Alternatively, cookie information maybe displayed directly within the information tab 210C. In some cases,other information, different from or in addition to that set forthabove, may be presented in the page information bubble 205C.

FIG. 2D illustrates an application window 200D with a page informationbubble 205D. The page information bubble 205D includes tabs forinformation 210D, permissions 215D, and connection 220D, where the usermay review or edit the associated information. As shown, the connectiontab 210D is selected. The connection tab 210D includes identity,encryption, and certificate details. In some examples, one or more ofthe identity, encryption, or certificate details may be presented in theinformation tab 210D instead of the connection tab 220D.

FIG. 2E illustrates an application window 200E with a page informationbubble 205E. The page information bubble 205E includes tabs forinformation 210E, permissions 215E, and connection 220E, where the usermay review or edit the associated information. As shown, the permissionstab 215E is selected. Within the permissions tab 215E, multiplecheckboxes for granting or denying various permissions (e.g., “Showimages,” “Run JavaScript,” etc.) to the currently displayed page arepresented. In some cases, one or more of the checkboxes may be coupledwith additional information or prompts. For example the “Use yourcamera” permission prompt may be coupled with a dropdown menu forselecting which of multiple cameras should be used. The “Store cookies”permission prompt may be coupled with an indication of cookies that arestored and/or a hyperlink for more information about the stored cookies.

FIG. 2F illustrates an application window 200F having an omnibox 225 anda chip 250F adjacent to the omnibox. The chip 250F may display atop-level domain of a page displayed in the active tap of theapplication window 200F. The page information bubble 205F may bepresented adjacent to the chip. The page information bubble 205F mayinclude a header region 240F indicating the top-level domain and whetherthe identity of the page is verified. Also, the chip 250F may include alock icon indicating that the page is secure. The header region 240F mayinclude a toolbar and/or a tabstrip.

FIG. 2G is similar to FIG. 2F and illustrates an application window 200Ghaving an omnibox 225G, a chip 250G, and a page information bubble 205Gwith a header region 240G. The permissions tab is displayed in the pageinformation bubble 205G. A permission request 245G to which the user hasnot yet responded may be visually indicated, for example, by drawing abox around the permission request, as shown, or highlighting thepermission request.

FIGS. 3A-3L illustrate example user interfaces for managing permissionsof an application. The application may be a web browser or any otherapplication.

Advantageously, implementations of the subject technology may usecleaner, human-readable language in communicating permissionsinformation to the user. The page information bubble dialog box may besimplified by removing some combination boxes and distinguishing betweenthe user's options and default selections. Permission grants may be mademore visible so that pages may not need to animate arrows pointing outthe infobars to the users. In some cases, permissions for core elementsof the modern web (e.g., images and JavaScript) may be grantedautomatically without prompting the user. The permissions may includeone or more of the following: “allow local data to be set,” “keep localdata only until I quit my browser,” “block sites from setting any data,”“block third-party cookies and site data,” “show all images,” “do notshow any images,” or “allow all sites to run JavaScript.”

FIG. 3A illustrates an example application window 300A displaying a pagerequesting permissions. As shown, in the application window 300A,multiple permissions prompts are presented at the top of the page,cluttering the interface and possibly overwhelming the user. Also, dueto the clutter at the top of the page, reviewing the information on thepage may be inconvenient for the user. Some aspects of the subjecttechnology are directed toward improvements of the interface of theapplication window 300A of FIG. 3A.

FIG. 3B illustrates an example application window 300B displaying a pagerequesting permissions. However, unlike application window 300A of FIG.3A, the application window 300B of FIG. 3B places the permissionrequests into a page information bubble 305B. Also, the “deny” and“allow” buttons of FIG. 3A are replaced with checkboxes in the pageinformation bubble 305B of FIG. 3B, resulting in a less cluttered andeasier to read and review interface. Furthermore, the header of the pageinformation bubble 305B indicates that the identity of the pagedisplayed in the active tab of the application window 300B is verified,possibly making the user feel safer in granting permissions to the page.

FIG. 3C illustrates an example application window 300C displaying a pagerequesting permissions. In FIG. 3C, a single permission to “use yourlocation” is requested in a permission bubble 305C adjacent to theomnibox 325C. Alternatively, a URL input box may replace the omnibox325C. The lock icon in the omnibox indicates that the displayed pagerequesting the permission to “use your location” is secure, possiblymaking the user feel safer in granting the permission.

FIG. 3D illustrates an example application window 300D displaying a pagerequesting permissions. As shown, multiple permissions (e.g., “Use yourcomputer's location,” “Use your camera and microphone,” etc.) arerequested in the permission bubble 305D adjacent to the omnibox 325D.Alternatively, a URL input box may replace the omnibox 325D. The lockicon in the omnibox indicates that the displayed page requesting themultiple permissions is secure, possibly making the user feel safer ingranting some or all of the requested permissions. As shown, in FIG. 3D,by default, all of the requested permissions in the permission bubble305D may be selected and the user may select the ok button 310D to closethe permission bubble 305D.

FIG. 3E illustrates an example application window 300E similar to theapplication window 300D of FIG. 3D. As shown, the application window300E includes an omnibox 325E (which may be replaced with a URL inputbox) and a permission bubble 305E with an ok button 310E. However, someof the requested permissions (e.g., “Use your camera and microphone)have been de-selected by the user to deny the page the de-selectedrequested permissions.

FIG. 3F illustrates an example application window 300F similar to theapplication windows 300D/300E of FIGS. 3D and 3E. As shown, theapplication window 300F includes an omnibox 325F (which may be replacedwith a URL input box) and a permission bubble 305F with an ok button310F. However, all of the requested permissions have been de-selected bythe user to deny the page all of the requested permissions.Alternatively, the user may deny the page all of the requestedpermissions by clicking anywhere outside the permission bubble305D/305E/305F causing the permission bubble 305D/305E/305F to bedismissed.

FIG. 3G illustrates an application window 300G with a page informationbubble 305G. The page information bubble 305G includes tabs forinformation 310G, permissions 315G, and connection 320G, where the usermay review or edit the associated information. As shown, the permissionstab 215E is selected. Within the permissions tab 315G, multiplecheckboxes for granting or denying various permissions (e.g., “Showimages,” “Run JavaScript,” etc.) to the currently displayed page arepresented. In some cases, one or more of the checkboxes may be coupledwith one or more dropdown menus. For example the “Use your camera andmicrophone” permission prompt may be coupled with dropdown menu(s) 330Gfor selecting which of multiple cameras and/or which of multiplemicrophones should be used.

FIG. 3H illustrates an example application window 300H displaying a pagerequesting permissions. Some sensitive permissions, for example,permissions 305H to access a microphone, may be displayed in a tabindicator of the application window 300H when such permissions aregranted to a page displayed in the tab. As a result of this interface, auser may chronically be alerted that he/she is granting sensitivepermissions to a tab, even when the tab is inactive. If the user wishesto deny the permissions, for example, to engage in a privateconversation, the user may access the tab with the permissions to denythe permissions.

FIG. 3I illustrates an example application window 300I requesting asingle permission to “use your microphone” in permission bubble 305I.FIG. 3J illustrates an example application window 300J requestingpermissions to “Use your camera” and “Use your microphone” in permissionbubble 305J. In some cases, permissions to use a camera and a microphonemay be merged and in other cases, permissions to use a camera and amicrophone may be separated. As a result, a page for Voice Over InternetProtocol (VOIP) calling may request permission to use only themicrophone, a page for taking photographs may request permission to useonly the camera, and a page for video calling may request permission touse both the microphone and the camera.

FIG. 3K illustrates an example page information bubble 300K. The pageinformation bubble 305K displaying the permissions tab. As shown, the“show pop-ups” permission is de-selected. The blocked pop-ups that theassociated page is attempting to display are shown so that the user mayselect one or more of the blocked pop-ups if the user wishes to view theblocked pop-ups.

FIG. 3L illustrates an example page information bubble 300L similar tothe page information bubble 300K of FIG. 3K. However, the “show pop-ups”permission is selected in FIG. 3L. As a result, the pop-ups that wereblocked in FIG. 3L are now shown and, in some cases, may no longer beindicated in the page information bubble 300L. Instead, the pageinformation bubble 300L may inform the user that “Pop-ups are blocked bydefault but will now be shown for this site.”

FIGS. 4A-4B illustrate example windows of a web browsing application.

FIG. 4A illustrates an application window 400A. The application window400A may be a window of a web browser application or anotherapplication. As shown, the application window 400A includes a headerregion 402A and a page display region 416A. The page display region 416Adisplays a default homepage.

The header region 402A includes a back button 404A, a forward button406A, a stop button 408A, a home button 410A, an omnibox 412A, and achip 414A. The back button 404A, when selected, causes the applicationto display a previously displayed page in the page display region 416A.The forward button 406A, when selected, causes the application todisplay a next page in a sequence in the page display region 416A,undoing the operation of the back button 404A. The stop button 408A,when selected, causes the application to stop loading a currentlydisplayed page. The home button 410A, when selected, causes theapplication to display the default homepage in the page display region416A. The omnibox 412A allows a user to enter a URL or search queryinput for causing the page display region 416A to display a pagecorresponding to the URL or the search query. As shown, the user isentering a URL (“newspaper.com/articles/X-wins-election”) into theomnibox 412A. As shown, the chip 414A is blank. However, in some cases,the chip 414A may display information about a currently displayed pagein the page display region 416A, for example, its URL. After the userfinishes entering the URL in the omnibox 412A and presses the “Enter”key on the keyboard, the application window 400A of FIG. 4A maytransform into an application window 400B of FIG. 4B.

FIG. 4B illustrates the application window 400B, which may be presentedafter the user finishes entering the URL in the omnibox 412A of FIG. 4Aand presses the “Enter” key on the keyboard. Similarly to FIG. 4A, theapplication window 400B of FIG. 4B includes a header region 402B and apage display region 416B. The page display region 416B displays a pagecorresponding to the URL entered by the user in the omnibox 412A of FIG.4A.

The header region 402A includes a back button 404B, a forward button406B, a stop button 408B, a home button 410B, an omnibox 412B, and achip 414B. The back button 404B, the forward button 406B, the stopbutton 408B, and the home button 410B operate similarly to the backbutton 404A, the forward button 406A, the stop button 408A, and the homebutton 410A of FIG. 4A. As shown in FIG. 4B, the URL of the pagedisplayed in the page display region 416B is presented in the omnibox412B. The chip 414B presents other information about the URL, includingthe top-level domain of the URL (“newspaper.com”). In some cases, thechip 414B may also present a hierarchy of the URL (e.g.,“newspaper.com>X-wins-election”). In some cases, other user interfaceelements may be presented in the chip 414B. For instance, as shown, thechip 414B may include a closed lock icon to indicate that the pagedisplayed in the page display region 416B is secure or that a connectionto the page is strong. Alternatively, the chip 414B may include an openlock icon to indicate that the page displayed in the page display region416B is not secure or that the connection to the page is weak, and/or atop-level domain of the page displayed in the page display region 416B.Furthermore, while the chip 414B is illustrated as being to the right ofthe omnibox 412B, in some cases, the chip 414B may be to the left,above, below, or at any other side of the omnibox 412B. The chip 414Bmay have any of multiple functions. In some cases, selecting the chip414B may cause the root of the page displayed in the page display region416B to be displayed in the page display region 416B. In some cases,selecting the chip 414B may resurface the URL presented in the omnibox412B. Dragging the chip 414B to a bookmark button may cause a bookmarkto the page displayed in the page display region 416B (corresponding tothe URL presented in the omnibox 412B) to be created. Furthermore, thechip 414B may show security status information or any other statusinformation, such as whether the page is completely loaded or in theprocess of loading, whether the page is permitted to store cookies,whether the page is bookmarked, etc. Alternatively, some or all extrafunctionality may be kept in the “actions” area in the toolbar ratherthan on the chip 414B.

Advantageously, as a result of the implementations described in FIGS.4A-4B, the user may see information different from a URL in the omnibox412A/412B and may be prompted to learn that the omnibox 412A/412B mayaccept search query input(s) as well as URL input(s). Furthermore, theuser may be able to more easily see (e.g., in the omnibox 412B) thetop-level domain and the hierarchy of the URL to determine whether theURL is authentic (e.g., an authentic bank page) or inauthentic (e.g., ahacker imitating a bank page to obtain account numbers or passwords).

FIG. 5 illustrates an example computer 500 that may provide a userinterface for a web browsing application. The computer 500 may be alaptop computer, a desktop computer, a mobile phone, a tablet computer,a personal digital assistant (PDA), a digital music player, a smartwatch, etc.

As shown, the computer 500 includes a processing unit 502, a networkinterface 504, and a memory 506. The processing unit 502 includes one ormore processors. The processing unit 502 may include a centralprocessing unit (CPU), a graphics processing unit (GPU), or any otherprocessing unit. The processing unit 502 executes computer instructionsthat are stored in a computer-readable medium, for example, the memory506. The network interface 504 allows the computer 500 to transmit andreceive data in a network, for example, a local area network, a widearea network, a wired network, a wireless network, the Internet, acellular network, etc. The memory 506 stores data and/or instructions.The memory 506 may be one or more of a cache unit, a storage unit, aninternal memory unit, or an external memory unit. As illustrated, thememory 506 includes an application 508. The application 508 may be a webbrowser or any other application. As shown, the application 508 includesa page display module 510, an omnibox/chip presentation module 512, apermission/extension presentation module 514, and a permission requestmodule 516.

The page display module 510 stores instructions that may be executed bythe processing unit 502. When executing the page display module 510, theprocessing unit 502 receives, in an omnibox (e.g., omnibox 412A) of anapplication window (e.g., application window 400A), an input including aURL. The processing unit 502 presents, in a page display region (e.g.,page display region 416A/416B) of the application window, a pagecorresponding to the URL.

Simultaneously with or after executing the page display module 510, theprocessing unit may execute the omnibox/chip presentation module 512.When executing the omnibox/chip presentation module 512, the processingunit 502 presents, in the omnibox, the URL. The processing unit 502presents, in the chip, the essence or collapsed form of the URL. Theessence or collapsed form of the URL includes a representation of atop-level domain and a hierarchy of the URL. The essence of the URLincludes different text from the URL itself.

The permission/extension presentation module 514 stores instructionsthat may be executed by the processing unit 502 simultaneously with orafter executing the page display module 510. When executing thepermission/extension presentation module 514, the processing unit 502presents, in a header region (e.g., header region 402A/402B) of theapplication window and externally to the omnibox, one or more graphicalelements. The graphical elements (e.g., icons 105A.1-9 or icon 305H)represent permissions granted to the displayed page or extensions havingaccess to the page. The omnibox may include text and may lack graphicalelements distinct from the text.

The permission request module 516 stores instructions that may beexecuted by the processing unit 502 simultaneously with or afterexecuting the page display module 510. When executing the permissionrequest module 516, the processing unit 502 receives, via the pagedisplayed within the page request region, a request for one or morepermissions. The processing unit 502 provides, within a bubble (e.g.,bubble 205E, 205F, 205G, 305B, 305C, 305D, 305E, 305F, 305G, 3051, 305J)overlaying the page display region and adjacent to the header region ofthe application, a textual indication of the request for the one or morepermissions. The processing unit 502 receives, via the bubble, a userinput for granting or denying the request for at least one of the one ormore permissions.

FIG. 6 illustrates an example process 600 by which an essence of auniform resource locator may be presented.

The process 600 begins at step 610, where a computer receives, in anomnibox (e.g., omnibox 412A) of an application window (e.g., applicationwindow 400A) of the computer, an input including a URL.

In step 620, the computer presents, in a page display region (e.g., pagedisplay region 416A/416B) of the application window, a pagecorresponding to the URL.

In step 630, the computer presents, in the omnibox of the applicationwindow adjacent to the omnibox, the URL.

In step 640, the computer presents, in a chip (e.g., chip 414A/414B) ofthe application window adjacent to the omnibox, the essence of the URL.The essence of the URL includes a representation of the top-level domainand a hierarchy of the URL. The essence of the URL includes differenttext from the URL. The top-level domain includes domain(s) at thehighest level in the hierarchical Domain Name System (DNS) of theInternet. The hierarchy may include one or more additional domain(s) inaddition to the top-level domain. The essence of the URL includes textdifferent from the URL itself. The omnibox may include text and may lackgraphical elements representing permissions or extensions. Graphicalelement(s) (e.g., icons 105A.1-9) representing permissions or extensionsmay be presented in a header region of the application window andexternally to the omnibox

According to some examples, the computer may receive a selection of thechip. Responsive to the selection of the chip, the computer may present,in a bubble (e.g., bubble 205F or 205G) adjacent to the chip, page dataassociated with the page in the page display region. The bubble may be adropdown below the chip. The page data may include information aboutpage visiting history, information about cookies related to the page,information about permissions, information about connections, and/orinformation about extensions. The permissions may include permissions toshow images, permissions to access a microphone or camera, permissionsto determine a geographic location of the computer, permissions to runcode in a scripting language (e.g., JavaScript), permissions to run aplug-in, or permissions to store cookies. The permissions are editable(e.g., may be granted or denied) by a user of the computer. Theinformation about extensions may include a list of extensions running inthe application and having access to the page. The extensions in thelist of extensions are editable or removable by the user of thecomputer.

According to some implementations, the computer may receive, from thepage, a request for one or more permissions. The computer may present,in a bubble (e.g., bubble 205F or 205G) adjacent to the omnibox or thechip, the request for the one or more permissions for approval or denialby the user. In an event that the user fails to respond to the requestfor the one or more permissions during a predetermined time period(e.g., five minutes, ten minutes, one hour, etc.), the computer mayre-present the bubble after the expiration of the predetermined timeperiod.

The page may be presented in a tab of an application. A tab indicator ofthe tab of the application may include a graphical element (e.g.,graphical element 305H) indicating that a sensitive permission (e.g., apermission to access a camera, a microphone, or geographic locationinformation) was granted to the page. The computer may receive aselection of the graphical element. The computer may provide, inresponse to the selection of the graphical element, an interface forgranting or denying the sensitive permission to the page. After step640, the process 600 ends.

FIG. 7 illustrates an example process 700 by which permissions grantedto a page or an extension having access to the page may be presented.

The process 700 begins at step 710, where a computer instantiates anapplication window (e.g., application window 400A). The applicationwindow includes a header region (e.g., header region 402A) and a pagedisplay region (e.g., page display region 416A). The header regionincludes an omnibox (e.g., omnibox 412A).

In step 720, the computer receives an input via the omnibox. The inputincludes a URL (e.g., “example.com”) or a search query (e.g. “ski traveldestinations”).

In step 730, the computer presents, in the page display region, a pagein response to the received input.

In step 740, the computer presents, in the header region and externallyto the omnibox, one or more graphical elements. The graphical elementsrepresent permissions granted to the page (e.g., graphical element 305H)or extensions having access to the page (e.g., icons 105B.1-2). Theomnibox includes text and lacks graphical elements distinct from thetext. The text may include the URL or the search query received in theinput of step 720. Alternatively, the text may include the essence ofthe URL presented in the page display region in response to the input.The essence of the URL includes a representation of the top-level domainof the URL and a hierarchy of the URL. The essence of the URL includesdifferent text from the URL itself, and the URL itself may be presentedin a chip (e.g., chip 414B) adjacent to the omnibox.

In some cases, the computer may receive a selection of an overflowindicator or menu button (e.g., menu button 110A or 110B) of the headerregion. The computer may present, in response to the selection of theoverflow indicator or menu button and in a dropdown from the headerregion, additional graphical elements (e.g., icons 105B.3-9)representing additional permissions granted to the page or additionalextensions having access to the page. The additional graphical elementsare different from the graphical elements in the header region. Afterstep 740, the process 700 ends.

FIG. 8 illustrates an example process 800 by which a page may requestpermissions from a user.

The process 800 begins at step 810, where a computer running anapplication (e.g., application 508, associated with application windows400A/400B) presents a page within a page display region (e.g., pagedisplay region 416A/416B) of the application.

In step 820, the computer receives, via the page displayed within thepage display region, a request for one or more permissions. For example,the page may request permissions to show images, access a microphone orcamera, determine a geographic location of the computer, run code in ascripting language, run a plug-in, or store cookies.

In step 830, the computer provides, within a bubble (e.g., bubble 305B,305C, 305D, 305E or 305F) overlaying the page display region andadjacent to a header region (e.g., header region 402A/402B) of theapplication, a textual indication of the request for the one or morepermissions. The one or more permissions may include a singlepermission, and the bubble (e.g., bubble 305C) may include an allowbutton for granting the request for the single permission and a denybutton for denying the request for the single permission. Alternatively,the one or more permissions may include multiple permissions, and thebubble (e.g., bubble 305B, 305D, 305E or 305F) may include a list of themultiple permissions. Each permission in the list may be adjacent to acheck box for granting or denying the request for the adjacentpermission. Furthermore, the computer may present, within the bubble, anindication of the top-level domain of the page and an indication whetherthe top-level domain is verified.

In step 840, the computer receives, via the bubble, a user input forgranting or denying the request for at least one of the one or morepermissions. After step 840, the process 800 ends.

While examples of the subject technology are described herein as beingimplemented on a laptop or desktop computer with a mouse-basedinterface, the subject technology may also be implemented on othermachine(s) with other interface(s). For instance, the subject technologymay be implemented on a mobile device, such as a mobile phone or atablet computer, with a touch screen interface. Furthermore, in somecases, the user may have multiple tabs of the same domain open. Thepermission(s) may be synced across the multiple tabs, or different tabsmay have different permissions.

FIG. 9 conceptually illustrates an electronic system 900 with which someimplementations of the subject technology are implemented. For example,the computer 500 may be implemented using the arrangement of theelectronic system 900. The electronic system 900 can be a computer(e.g., a mobile phone, PDA), or any other sort of electronic device.Such an electronic system includes various types of computer readablemedia and interfaces for various other types of computer readable media.Electronic system 900 includes a bus 905, processing unit(s) 910, asystem memory 915, a read-only memory 920, a permanent storage device925, an input device interface 930, an output device interface 935, anda network interface 940.

The bus 905 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 900. For instance, the bus 905 communicativelyconnects the processing unit(s) 910 with the read-only memory 920, thesystem memory 915, and the permanent storage device 925.

From these various memory units, the processing unit(s) 910 retrievesinstructions to execute and data to process in order to execute theprocesses of the subject technology. The processing unit(s) can be asingle processor or a multi-core processor in different implementations.

The read-only-memory (ROM) 920 stores static data and instructions thatare needed by the processing unit(s) 910 and other modules of theelectronic system. The permanent storage device 925, on the other hand,is a read-and-write memory device. This device is a non-volatile memoryunit that stores instructions and data even when the electronic system900 is off. Some implementations of the subject technology use amass-storage device (for example a magnetic or optical disk and itscorresponding disk drive) as the permanent storage device 925.

Other implementations use a removable storage device (for example afloppy disk, flash drive, and its corresponding disk drive) as thepermanent storage device 925. Like the permanent storage device 925, thesystem memory 915 is a read-and-write memory device. However, unlikestorage device 925, the system memory 915 is a volatile read-and-writememory, such a random access memory. The system memory 915 stores someof the instructions and data that the processor needs at runtime. Insome implementations, the processes of the subject technology are storedin the system memory 915, the permanent storage device 925, or theread-only memory 920. For example, the various memory units includeinstructions for providing a user interface for an applicationdisplaying pages in accordance with some implementations. From thesevarious memory units, the processing unit(s) 910 retrieves instructionsto execute and data to process in order to execute the processes of someimplementations.

The bus 905 also connects to the input and output device interfaces 930and 935. The input device interface 930 enables the user to communicateinformation and select commands to the electronic system. Input devicesused with input device interface 930 include, for example, alphanumerickeyboards and pointing devices (also called “cursor control devices”).Output device interfaces 935 enables, for example, the display of imagesgenerated by the electronic system 900. Output devices used with outputdevice interface 935 include, for example, printers and display devices,for example cathode ray tubes (CRT) or liquid crystal displays (LCD).Some implementations include devices for example a touch screen thatfunctions as both input and output devices.

Finally, as shown in FIG. 9, bus 905 also couples electronic system 900to a network (not shown) through a network interface 940. In thismanner, the electronic system 900 can be a part of a network ofcomputers (for example a local area network (LAN), a wide area network(WAN), or an Intranet, or a network of networks, for example theInternet. Any or all components of electronic system 900 can be used inconjunction with the subject technology.

The above-described features and applications can be implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or moreprocessing unit(s) (e.g., one or more processors, cores of processors,or other processing units), they cause the processing unit(s) to performthe actions indicated in the instructions. Examples of computer readablemedia include, but are not limited to, CD-ROMs, flash drives, RAM chips,hard drives, EPROMs, etc. The computer readable media does not includecarrier waves and electronic signals passing wirelessly or over wiredconnections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storageor flash storage, for example, a solid-state drive, which can be readinto memory for processing by a processor. Also, in someimplementations, multiple software technologies can be implemented assub-parts of a larger program while remaining distinct softwaretechnologies. In some implementations, multiple software technologiescan also be implemented as separate programs. Finally, any combinationof separate programs that together implement a software technologydescribed here is within the scope of the subject technology. In someimplementations, the software programs, when installed to operate on oneor more electronic systems, define one or more specific machineimplementations that execute and perform the operations of the softwareprograms.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

These functions described above can be implemented in digital electroniccircuitry, in computer software, firmware or hardware. The techniquescan be implemented using one or more computer program products.Programmable processors and computers can be included in or packaged asmobile devices. The processes and logic flows can be performed by one ormore programmable processors and by one or more programmable logiccircuitry. General and special purpose computing devices and storagedevices can be interconnected through communication networks.

Some implementations include electronic components, for examplemicroprocessors, storage and memory that store computer programinstructions in a machine-readable or computer-readable medium(alternatively referred to as computer-readable storage media,machine-readable media, or machine-readable storage media). Someexamples of such computer-readable media include RAM, ROM, read-onlycompact discs (CD-ROM), recordable compact discs (CD-R), rewritablecompact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM,dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g.,DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SDcards, micro-SD cards, etc.), magnetic or solid state hard drives,read-only and recordable Blu-Ray® discs, ultra density optical discs,any other optical or magnetic media, and floppy disks. Thecomputer-readable media can store a computer program that is executableby at least one processing unit and includes sets of instructions forperforming various operations. Examples of computer programs or computercode include machine code, for example is produced by a compiler, andfiles including higher-level code that are executed by a computer, anelectronic component, or a microprocessor using an interpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some implementations areperformed by one or more integrated circuits, for example applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some implementations, such integrated circuits executeinstructions that are stored on the circuit itself.

As used in this specification and any claims of this application, theterms “computer”, “server”, “processor”, and “memory” all refer toelectronic or other technological devices. These terms exclude people orgroups of people. For the purposes of the specification, the termsdisplay or displaying means displaying on an electronic device. As usedin this specification and any claims of this application, the terms“computer readable medium” and “computer readable media” are entirelyrestricted to tangible, physical objects that store information in aform that is readable by a computer. These terms exclude any wirelesssignals, wired download signals, and any other ephemeral signals.

To provide for interaction with a user, implementations of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a cathode ray tube (CRT) or liquidcrystal display (LCD) monitor, for displaying information to the userand a keyboard and a pointing device, e.g., a mouse or a trackball, bywhich the user can provide input to the computer. Other kinds of devicescan be used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

The subject matter described in this specification can be implemented ina computing system that includes a back end component, e.g., as a dataserver, or that includes a middleware component, e.g., an applicationserver, or that includes a front end component, e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the subject matter described inthis specification, or any combination of one or more such back end,middleware, or front end components. The components of the system can beinterconnected by any form or medium of digital data communication,e.g., a communication network. Examples of communication networksinclude a local area network (LAN) and a wide area network (WAN), aninter-network (e.g., the Internet), and peer-to-peer networks (e.g., adhoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someaspects of the disclosed subject matter, a server transmits data (e.g.,an HTML page) to a client device (e.g., for purposes of displaying datato and receiving user input from a user interacting with the clientdevice). Data generated at the client device (e.g., a result of the userinteraction) can be received from the client device at the server.

It is understood that any specific order or hierarchy of steps in theprocesses disclosed is an illustration of example approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged, or that allillustrated steps be performed. Some of the steps may be performedsimultaneously. For example, in certain circumstances, multitasking andparallel processing may be advantageous. Moreover, the separation ofvarious system components illustrated above should not be understood asrequiring such separation, and it should be understood that thedescribed program components and systems can generally be integratedtogether in a single software product or packaged into multiple softwareproducts.

Various modifications to these aspects will be readily apparent, and thegeneric principles defined herein may be applied to other aspects. Thus,the claims are not intended to be limited to the aspects shown herein,but is to be accorded the full scope consistent with the languageclaims, where reference to an element in the singular is not intended tomean “one and only one” unless specifically so stated, but rather “oneor more.” Unless specifically stated otherwise, the term “some” refersto one or more. Pronouns in the masculine (e.g., his) include thefeminine and neuter gender (e.g., her and its) and vice versa. Headingsand subheadings, if any, are used for convenience only and do not limitthe subject technology.

A phrase, for example, an “aspect” does not imply that the aspect isessential to the subject technology or that the aspect applies to allconfigurations of the subject technology. A disclosure relating to anaspect may apply to all configurations, or one or more configurations. Aphrase, for example, an aspect may refer to one or more aspects and viceversa. A phrase, for example, a “configuration” does not imply that suchconfiguration is essential to the subject technology or that suchconfiguration applies to all configurations of the subject technology. Adisclosure relating to a configuration may apply to all configurations,or one or more configurations. A phrase, for example, a configurationmay refer to one or more configurations and vice versa.

What is claimed is:
 1. A method for presenting information in a headerregion of an application, the method comprising: receiving, in anomnibox of an application window of a computer, an input comprising auniform resource locator (URL); presenting, in a page display region ofthe application window, a page corresponding to the URL; presenting, inthe omnibox, the URL; presenting, in a chip of the application windowadjacent to the omnibox, an essence of the URL and connectioninformation associated with the page, the essence of the URL comprisinga representation of a top-level domain and a hierarchy of the URL, theessence of the URL comprising different text from the URL.
 2. The methodof claim 1, further comprising: receiving a selection of the chip; andresponsive to the selection of the chip, presenting, in a bubbleadjacent to the chip, page data associated with the page in the pagedisplay region, the page data comprising information about page visitinghistory, information about cookies related to the page, informationabout permissions, information about connections, and information aboutextensions.
 3. The method of claim 2, wherein the permissions comprisepermissions to show images, permissions to access a microphone orcamera, permissions to determine a geographic location of the computer,permissions to run code in a scripting language, permissions to run aplug-in, or permissions to store cookies, and wherein the permissionsare editable by a user of the computer.
 4. The method of claim 2,wherein the information about extensions comprises a list of extensionsrunning in the application and having access to the page, and whereinthe extensions in the list of extensions are editable or removable by auser of the computer.
 5. The method of claim 2, wherein the bubbleadjacent to the chip comprises a dropdown below the chip.
 6. The methodof claim 1, further comprising: receiving, from the page, a request forone or more permissions; and presenting, in a bubble adjacent to theomnibox or the chip, the request for the one or more permissions forapproval or denial by a user of the computer.
 7. The method of claim 6,further comprising: in an event that the user fails to respond to therequest for the one or more permissions for approval or denial by theuser during a predetermined time period, re-presenting the bubble afterthe expiration of the predetermined time period.
 8. The method of claim1, wherein the page is presented in a tab of the application, andwherein a tab indicator of the tab of the application comprises angraphical element indicating that a sensitive permission was granted tothe page, wherein the sensitive permission comprises one of access to acamera, access to a microphone, or ability to determine a geographiclocation of the computer.
 9. The method of claim 8, further comprising:receiving a selection of the graphical element; and providing, inresponse to the selection of the graphical element, an interface forgranting or denying the sensitive permission to the page.
 10. The methodof claim 1, wherein the omnibox comprises text and lacks graphicalelements representing permissions or extensions, and one or moregraphical elements representing permissions or extensions are presentedin a header region of the application window and externally to theomnibox.
 11. A non-transitory computer-readable medium comprisinginstructions which, when executed by a computer, cause the computer toimplement a method, the method comprising: instantiating an applicationwindow, the application window comprising a header region and a pagedisplay region, the header region comprising an omnibox; receiving aninput via the omnibox, wherein the input comprises a uniform resourcelocator (URL) or a search query; presenting, in the page display region,a page in response to the received input; presenting, in the headerregion and externally to the omnibox, one or more graphical elements,the graphical elements representing permissions granted to the page orextensions having access to the page, wherein the omnibox comprises textand lacks graphical elements distinct from the text.
 12. Thenon-transitory computer-readable medium of claim 11, wherein the textcomprises the URL or the search query of the received input.
 13. Thenon-transitory computer-readable medium of claim 11, wherein the textcomprises an essence of a URL of the page presented in the page displayregion, the essence of the URL of the page comprising a representationof a top-level domain and a hierarchy of the URL of the page, theessence of the URL of the page comprising different text from the URL ofthe page.
 14. The non-transitory computer-readable medium of claim 13,the method further comprising: presenting, in a chip of the applicationwindow adjacent to the omnibox, the URL of the page.
 15. Thenon-transitory computer-readable medium of claim 11, the method furthercomprising: receiving a selection of an overflow indicator of the headerregion; and presenting, in a dropdown from the header region andresponsive to the selection of the overflow indicator, additionalgraphical elements representing additional permissions granted to thepage or additional extensions having access to the page, wherein theadditional graphical elements are different from the graphical elementspresented in the header region.
 16. A system comprising: one or moreprocessors; and a memory comprising instructions which, when executed bythe one or more processors, cause the one or more processors toimplement a method, the method comprising: presenting a page within apage display region of an application; receiving, via the page displayedwithin the page display region, a request for one or more permissions;providing, within a bubble overlaying the page display region andadjacent to a header region of the application, a textual indication ofthe request for the one or more permissions; and receiving, via thebubble, a user input for granting or denying the request for at leastone of the one or more permissions.
 17. The system of claim 16, whereinthe one or more permissions comprise a single permission, and whereinthe bubble comprises an allow button for granting the request for thesingle permission and a deny button for denying the request for thesingle permission.
 18. The system of claim 16, wherein the one or morepermissions comprise plural permissions, and wherein the bubblecomprises a list of the plural permissions, wherein each permission inthe list is adjacent to a check box for granting or denying the requestfor the adjacent permission.
 19. The system of claim 16, the methodfurther comprising: presenting, within the bubble, an indication of atop-level domain of the page within the page display region and anindication whether an identity of the top-level domain is verified. 20.The system of claim 16, wherein the one or more permissions comprise oneor more of permissions to show images, permissions to access amicrophone or camera, permissions to determine a geographic location ofthe computer, permissions to run code in a scripting language,permissions to run a plug-in, or permissions to store cookies.